home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 24
/
Aminet 24 (1998)(GTI - Schatztruhe)[!][Apr 1998].iso
/
Aminet
/
comm
/
mail
/
AEMail.lha
/
aemail143
/
INSTALL.TXT
< prev
next >
Wrap
Text File
|
1998-01-15
|
25KB
|
477 lines
INSTALLATION OF AEMAIL
(January 15, 1998)
The AEMail Install Script uses the Installer program first provided by
Commodore and later revised by Amiga Technologies. You should use the
Install_AEMail script to install AEMail. It is not recommended that you
attempt to install AEMail by hand since some actions are necessary through
the install script. This is especially true if you are attempting to
install a registered version with the supplied diskette!
Installer and Installer project icon
(c) Copyright 1995-96 Escom AG. All Rights Reserved.
Reproduced and distributed under license from Escom AG.
INSTALLER SOFTWARE IS PROVIDED "AS-IS" AND SUBJECT TO CHANGE;
NO WARRANTIES ARE MADE. ALL USE IS AT YOUR OWN RISK. NO LIABILITY
OR RESPONSIBILITY IS ASSUMED.
To install AEMail simply double click on the "Install_AEMail icon". The
install script provides two user levels that the user can choose:
Intermediate (control of configuration parameters only)
Expert (control of configuration and where files are placed)
The Install script makes an attempt to determine which TCP/IP stack that
you have installed. This controls which defaults will be taken. The way
the install scripts knows which TCP/IP stacks are present is as follows
(you must have installed the particular stack before installing AEMail):
AmiTCP: This is controlled by the presence of the AmiTCP: assign
statement and the presence of the AmiTCP:bin drawer.
Miami: This is controlled by the presence of the Miami: assign
statement. When you installed Miami you should have let
the install create the Miami: assign. This was only
available under later versions of Maimi.
While the Miami: assign is not an absolute requirement
if you are using Miami, it is required if you intend
to use the supplied "startnet.miami" and "stopnet.miami"
scripts supplied with this archive. The scripts will
not even be moved to your AEMail drawer if the Miami:
assign is not present.
TermiteTCP: This is controlled by the presence of the TermiteTCP.prefs
envronomental variable. Also, if you want to pick up
some of the other TermiteTCP variables, such as email
address, you must have run TermiteTCP prior to installing
AEMail (TermiteTCP does not have to be online, however).
The action that takes place at during the install is slightly different
depending on whether AmiTCP has been installed or not. The installation
script determines if AmiTCP is installed by checking for an assignment to
AmiTCP:. This AmiTCP: assignment was automatically created when you
installed AmiTCP.
If the AmiTCP: assignment is present, it will determine where the
installation script will place the AEMail executable. For AmiTCP the
executable is placed in the AmiTCP:bin drawer. If this drawer is not
present, the placement of the executable defaults to an "AEMail" drawer
(created by the script if it does not already exist) on the largest
partition on your hard drive.
If you wish to control where AEMail will be placed, you will need to
execute the Install script at the "Expert" user level.
The reason that AEMail is placed in the AmiTCP:bin drawer if the AmiTCP:
assignment is present, is that the assumption is made that you are using
AmiTCP. The "startnet" and "stopnet" scripts should be in the same
directory that contains AEMail if they are to work without modification.
If you select the Intermediate user level, the following actions will be
taken:
The AEMail executable file will be placed in AmiTCP:bin or, if the
AmiTCP: assignment is not present, on the largest partition on
your hard drive.
Note: No special directory will be created if AmiTCP:bin is
present, otherwise a directory called "AEMail" will be created
for containing the AEMail executable. When the installation
script terminates it will tell you where it placed the AEMail
executable.
The AREXX scripts StartNet.Miami and StopNet.Miami will also
be moved to this drawer if you have Miami installed on your
system as determined by a Miami: assignment.
Your AEMail mail directory will normally be a directory called
AEMail_Mail in AmiTCP: or, if AmiTCP: was not present, in the
AEMail directory. The AEMail mail directory will be assigned to
AEMAIL:. If an AEMAIL: assignment already exists, that directory
will be used as the mail directory except that it will be
renamed to AEMail_Mail if it had been named something else.
This operation is automatic and makes updating the AEMail program
easy without disturbing your existing mail files.
The documentation files that you want copied will be copied to a drawer
called "documentation" in the drawer which contains the AEMail
executable.
If you want the AEMail.readme file, it will be copied to the directory
containing your AEMail executable.
A handy registration form called "registration.form" will be available
in your main AEMail directory. It has an icon which, if you double
click on it, will use the "PrintFiles" program in your SYS:Tools
directory to print out the registration form.
If you are running under AmigaDos 3.0 or greater, the supplied
mailcap file will be copied to the AEMail_Mail directory.
No mailcap file will be copied if you are using AmigaDos 2.1.
An AEMAIL: assign statement will automatically be placed in your
S:User-Startup file.
An "ASSIGN C: SYS:REXXC ADD" will also be added to your s:User-Startup
file to provide a path to your AREXX commands.
As noted above, the default drawer in which your documentation is placed is
a drawer called "documentation" in the drawer containing your AEMail
executable. This is different from prior versions where the documentation
files were placed in the same drawer as the AEMail executable. Your old
documentation files WILL BE deleted by the installation script. If you
want these retained you will have to re-name them yourself.
If you select either user level you will also be able to provide
configuration data that will be stored in the Tool Types parameters of the
AEMail icon. Further, if the AEMAIL: assignment existed at the start of
the installation that assignment will be used. However, if the mail
directory had been called something else, you will be asked if you want to
rename it to AEMail_Mail. If you select NO, the directory will not be
renamed; however, a new AEMail_Mail directory will be created in the same
parent directory and used for the AEMAIL: assignment.
In addition to what is available for the Intermediate user, the Expert user
will be able to select what directories will be used and will be able to
copy the documentation files to a directory of his/her choice. The Expert
user will also be able to select an alternate location for a pre-existing
mailcap file and, if running under AmigaDos 2.1, will be able to build
their own mailcap file.
IF YOU ARE UPDATING FROM A PREVIOUS VERSION OF AEMail, it is recommended
that you install at the Intermediate level. That will insure that all of
your old assignments and mail files will be available. Also, you should
not try to configure AEMail with the Install script since you already have
a configuration file assigned.
The one exception to this is if you are updating from a version of AEMail
below 1.10. In this case you will HAVE to install at the Expert level in
order to locate where your old AEMail installation was placed.
Certain configuration parameters must be provided before AEMail will run.
These configuration parameters are provided either by Tool Types in the
AEMail icon or through a special configuration screen when you first run
AEMail and saved in an aemail.cnfg file in the S: directory. For a full
dis